Network-based media processing (nbmp) workflow management through 5g framework for live uplink streaming (flus) control

ABSTRACT

A method, computer program, and computer system is provided for establishing Network-Based Media Processing (NBMP) workflow through 5G Framework for Live Uplink Streaming (FLUS) control. A plurality of sinks and network capabilities of a network platform are discovered through a plurality of 5G FLUS discovery and capabilities mechanisms. An NBMP workflow is created, updated, retrieved, and deleted through a control interface comprising a FLUS source and a FLUS sink, whereby the 5G FLUS control is extended to support tunneling information between an NBMP source and an NBMP workflow manager.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a Continuation Application of U.S. application Ser.No. 17/242,968, filed on Apr. 28, 2021, which is a ContinuationApplication of U.S. application Ser. No. 17/034,778, filed on Sep. 28,2020, which claims priority based on U.S. Provisional Application No.63/001,946 (filed Mar 30, 2020), and was issued as U.S. Pat. No.11,063,992, the entirety of which is incorporated herein.

FIELD

This disclosure relates generally to field of data processing, and moreparticularly to media processing.

BACKGROUND

The Network-based Media Processing (NBMP) standard was developed toaddress fragmentation and offer a unified way to perform mediaprocessing on top of any cloud platform and on any IP network. The 3rdGeneration Partnership Project (3GPP) Framework for Live UplinkStreaming (FLUS) protocol provides a mechanism for uplink streaming ofmultimedia content from a source device to the network andsending/distributing that content to one or more destinations.

SUMMARY

Embodiments relate to a method, system, and computer readable medium forestablishing an NBMP workflow through 5G FLUS control. According to oneaspect, a method for establishing an NBMP workflow through 5G FLUScontrol is provided. The method may include discovering a plurality ofsinks and network capabilities of a network platform through a pluralityof 5G FLUS discovery and capabilities mechanisms. An NBMP workflow iscreated, updated, retrieved, and deleted through a FLUS source-sinkcontrol interface, whereby the 5G FLUS control is extended to supporttunneling information between an NBMP source and an NBMP workflowmanager.

According to another aspect, a computer system for establishing an NBMPworkflow through 5G FLUS control is provided. The computer system mayinclude one or more processors, one or more computer-readable memories,one or more computer-readable tangible storage devices, and programinstructions stored on at least one of the one or more storage devicesfor execution by at least one of the one or more processors via at leastone of the one or more memories, whereby the computer system is capableof performing a method. The method may include discovering a pluralityof sinks and network capabilities of a network platform through aplurality of FLUS discovery and capabilities mechanisms. An NBMPworkflow is created, updated, retrieved, and deleted through a FLUSsource-sink control interface, whereby the FLUS control is extended tosupport tunneling information between an NBMP source and an NBMPworkflow manager.

According to yet another aspect, a computer readable medium forestablishing an NBMP workflow through 5G FLUS control is provided. Thecomputer readable medium may include one or more computer-readablestorage devices and program instructions stored on at least one of theone or more tangible storage devices, the program instructionsexecutable by a processor. The program instructions are executable by aprocessor for performing a method that may accordingly includediscovering a plurality of sinks and network capabilities of a networkplatform through a plurality of FLUS discovery and capabilitiesmechanisms. An NBMP workflow is created, updated, retrieved, and deletedthrough a FLUS source-sink control interface, whereby the 5G FLUScontrol is extended to support tunneling information between an NBMPsource and an NBMP workflow manager.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects, features and advantages will become apparentfrom the following detailed description of illustrative embodiments,which is to be read in connection with the accompanying drawings. Thevarious features of the drawings are not to scale as the illustrationsare for clarity in facilitating the understanding of one skilled in theart in conjunction with the detailed description. In the drawings:

FIG. 1 illustrates a networked computer environment according to atleast one embodiment;

FIG. 2 is a block diagram of a system for establishing an NBMP workflowthrough 5G FLUS control, according to at least one embodiment;

FIG. 3 is an operational flowchart illustrating the steps carried out bya program for establishing an NBMP workflow through 5G FLUS control,according to at least one embodiment;

FIG. 4 is a block diagram of internal and external components ofcomputers and servers depicted in FIG. 1 according to at least oneembodiment;

FIG. 5 is a block diagram of an illustrative cloud computing environmentincluding the computer system depicted in FIG. 1 , according to at leastone embodiment; and

FIG. 6 is a block diagram of functional layers of the illustrative cloudcomputing environment of FIG. 5 , according to at least one embodiment.

DETAILED DESCRIPTION

Detailed embodiments of the claimed structures and methods are disclosedherein; however, it can be understood that the disclosed embodiments aremerely illustrative of the claimed structures and methods that may beembodied in various forms. Those structures and methods may, however, beembodied in many different forms and should not be construed as limitedto the exemplary embodiments set forth herein. Rather, these exemplaryembodiments are provided so that this disclosure will be thorough andcomplete and will fully convey the scope to those skilled in the art. Inthe description, details of well-known features and techniques may beomitted to avoid unnecessarily obscuring the presented embodiments.

Embodiments relate generally to the field of data processing, and moreparticularly to media processing. The following described exemplaryembodiments provide a system, method and computer program to, amongother things, provide a mechanism for an NBMP Source to fully controlthe NBMP Workflow Manager through the FLUS control path. Therefore, someembodiments have the capacity to improve the field of computing byproviding an architecture in which the source client is an NBMP sourceto manage the workflow through the FLUS control interface.

As previously described, the Network-based Media Processing (NBMP)standard was developed to address fragmentation and offer a unified wayto perform media processing on top of any cloud platform and on any IPnetwork. The 3rd Generation Partnership Project (3GPP) Framework forLive Uplink Streaming (FLUS) protocol provides a mechanism for uplinkstreaming of multimedia content from a source device to the network andsending/distributing that content to one or more destinations. In theNBMP standard, the NBMP Source may be the entity providing the workflowdescription to Workflow Manager to create, run, manage and monitor amedia workflow. The interaction between NBMP Source and Workflow Managermay be through a set of NBMP Operation Application ProgrammingInterfaces (APIs). In the case of the 3GPP FLUS protocol, the sourcedevice of media streams may establish an uplink session with a sinkthrough the network. The FLUS APIs may allow the source device tocontrol the session and also the Sink to provide feedback or remotecontrol of the source device. The 3GPP FLUS protocol may support theinclusion of an NBMP Workflow Description Document (WDD) as part of thesession control update by the source device. However, the protocol maynot include the interaction between the source device and the sink forthe management of the NBMP Workflow after the establishment of theWorkflow. Furthermore, it may not provide an architecture for the NBMPWorkflow Manager or Tasks to provide reporting and notification to thesource device so that it can receive feedback from the running NBMPWorkflow to be able to dynamically manage and modify the workflow. Itmay be advantageous, therefore, to provide a mechanism for NBMP Sourceto fully control the NBMP Workflow Manager through the FLUS control pathby using cloud-based workflow processing for an uplink streaming withthe control being at the client device which is the source of theuplink. This may provide an architecture in which the source client isan NBMP source to manage the workflow through the FLUS controlinterface.

Aspects are described herein with reference to flowchart illustrationsand/or block diagrams of methods, apparatus (systems), and computerreadable media according to the various embodiments. It will beunderstood that each block of the flowchart illustrations and/or blockdiagrams, and combinations of blocks in the flowchart illustrationsand/or block diagrams, can be implemented by computer readable programinstructions.

The following described exemplary embodiments provide a system, methodand computer program that allows for establishing an NBMP workflowthrough 5G FLUS control. Referring now to FIG. 1 , a functional blockdiagram of a networked computer environment illustrating a mediaprocessing system 100 (hereinafter “system”) for establishing an NBMPworkflow through 5G FLUS control. It should be appreciated that FIG. 1provides only an illustration of one implementation and does not implyany limitations with regard to the environments in which differentembodiments may be implemented. Many modifications to the depictedenvironments may be made based on design and implementationrequirements.

The system 100 may include a computer 102 and a server computer 114. Thecomputer 102 may communicate with the server computer 114 via acommunication network 110 (hereinafter “network”). The computer 102 mayinclude a processor 104 and a software program 108 that is stored on adata storage device 106 and is enabled to interface with a user andcommunicate with the server computer 114. As will be discussed belowwith reference to FIG. 4 the computer 102 may include internalcomponents 800A and external components 900A, respectively, and theserver computer 114 may include internal components 800B and externalcomponents 900B, respectively. The computer 102 may be, for example, amobile device, a telephone, a personal digital assistant, a netbook, alaptop computer, a tablet computer, a desktop computer, or any type ofcomputing devices capable of running a program, accessing a network, andaccessing a database.

The server computer 114 may also operate in a cloud computing servicemodel, such as Software as a Service (SaaS), Platform as a Service(PaaS), or Infrastructure as a Service (IaaS), as discussed below withrespect to FIGS. 5 and 6 . The server computer 114 may also be locatedin a cloud computing deployment model, such as a private cloud,community cloud, public cloud, or hybrid cloud.

The server computer 114, which may be used for establishing an NBMPworkflow through 5G FLUS control is enabled to run an NBMP FLUS ControlProgram 116 (hereinafter “program”) that may interact with a database112. The NBMP FLUS Control Program method is explained in more detailbelow with respect to FIG. 3 . In one embodiment, the computer 102 mayoperate as an input device including a user interface while the program116 may run primarily on server computer 114. In an alternativeembodiment, the program 116 may run primarily on one or more computers102 while the server computer 114 may be used for processing and storageof data used by the program 116. It should be noted that the program 116may be a standalone program or may be integrated into a larger NBMP FLUScontrol program.

It should be noted, however, that processing for the program 116 may, insome instances be shared amongst the computers 102 and the servercomputers 114 in any ratio. In another embodiment, the program 116 mayoperate on more than one computer, server computer, or some combinationof computers and server computers, for example, a plurality of computers102 communicating across the network 110 with a single server computer114. In another embodiment, for example, the program 116 may operate ona plurality of server computers 114 communicating across the network 110with a plurality of client computers. Alternatively, the program mayoperate on a network server communicating across the network with aserver and a plurality of client computers.

The network 110 may include wired connections, wireless connections,fiber optic connections, or some combination thereof. In general, thenetwork 110 can be any combination of connections and protocols thatwill support communications between the computer 102 and the servercomputer 114. The network 110 may include various types of networks,such as, for example, a local area network (LAN), a wide area network(WAN) such as the Internet, a telecommunication network such as thePublic Switched Telephone Network (PSTN), a wireless network, a publicswitched network, a satellite network, a cellular network (e.g., a fifthgeneration (5G) network, a long-term evolution (LTE) network, a thirdgeneration (3G) network, a code division multiple access (CDMA) network,etc.), a public land mobile network (PLMN), a metropolitan area network(MAN), a private network, an ad hoc network, an intranet, a fiberoptic-based network, or the like, and/or a combination of these or othertypes of networks.

The number and arrangement of devices and networks shown in FIG. 1 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 1 . Furthermore, two or more devices shown in FIG. 1 maybe implemented within a single device, or a single device shown in FIG.1 may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) of system100 may perform one or more functions described as being performed byanother set of devices of system 100.

Referring now to FIG. 2 , a block diagram of a 3GPP FLUS architecture200 is depicted. The 3GPP FLUS architecture 200 may include a first userenvironment 202 and a second user environment 204. The first userenvironment 202 may include an NBMP source 205, one or more capturedevices 206 and a FLUS source 208. The FLUS source 208 may include acontrol source 210, a media source 212, an assistance receiver 214, anda remote control target 216. The second user environment 204 may includea FLUS sink 218, an NBMP workflow manager 219, an assistance sender 220,an NBMP workflow 221, and a remote controller 222. The FLUS sink 218 mayinclude a control sink 224 and a media sink 226.

The NBMP Source 205 may define a workflow processing at the Network orthe destination device (i.e., the second user environment 204). The NBMPWorkflow Manager 219 and the NBMP Workflow 221 may reside on the networkor the destination device (i.e., the second user environment 204). TheNBMP workflow 221 may include several stages. In stage 1 (sinkdiscovery), the NBMP Source 205 may discovers the existing sinks bymaking a request to the FLUS source 208, which may consequently be sentto a FLUS discovery point. The FLUS discovery point may provide the listof sinks to FLUS source 208, which may consequently provide it to NBMPSource 205.

In stage 2 (capabilities discovery), the NBMP Source 205 may request thecapabilities of one of the provided sinks in the sink list. The FLUSsource 208 may pass the request to the FLUS sink 218. The FLUS sink 218may either have the capabilities of its platform or may request the NBMPWorkflow Manager 219 get the current platform capabilities. It may beappreciated that the capabilities of the platform may change dependingon the current running workflows. The capabilities description of theplatform or a link to it may be returned to the NBMP source 205 via theFLUS sink 218 and FLUS source 208. The stage 2 response may include anNBMP scheme identifier indicating that the Workflow Manager supportsNBMP, a URL for the location (URI) from which the capabilities of theplatform can be retrieved, and a capability description document thatdescribes the capabilities of the platform.

In stage 3 (workflow creation), the NBMP source 205 may request thecreation of the NBMP workflow 221 through the FLUS source 208 and theFLUS sink 218. Since during Stage 3, the NBMP workflow 221 might becreated right away, rejected, or created with a possible delay, theStage 3 response may include either HTTP response code 201 and WDD, HTTPresponse code 4xx or 5xx and optionally a WDD, or HTTP response code 202and a HTTP header Retry-After value.

Referring now to FIG. 3 , an operational flowchart 300 illustrating thesteps carried out by a program for establishing an NBMP workflow through5G FLUS control is depicted. FIG. 3 may be described with the aid ofFIGS. 1 and 2 . As previously described, the NBMP FLUS Control Program116 (FIG. 1 ) may provide an architecture in which the source client isan NBMP source to manage the workflow through the FLUS controlinterface.

At 302, a plurality of sinks and network capabilities of a networkplatform are discovered through a plurality of FLUS discovery andcapabilities mechanisms. The network capabilities may either bedescribed by an identifier and by a URL location from which descriptionsof the network capabilities can be retrieved or may be explicitlyincluded in discovery responses. In operation, the NBMP Source 205 (FIG.2 ) may discover the existing sinks by making a request to the FLUSsource 208 (FIG. 2 ). A list of the sinks may be returned to the NBMPSource 205.

At 304, an NBMP workflow is created, updated, retrieved, and deletedthrough a control interface comprising a FLUS source and a FLUS sink.The 5G FLUS control is extended to support tunneling information betweenan NBMP source and an NBMP workflow manager. In operation, the NBMPsource 205 (FIG. 2 ) may request the creation of the NBMP workflow 221(FIG. 2 ) through the FLUS source 208 (FIG. 2 ) and the FLUS sink 218(FIG. 2 ). An HTTP status code and WDD may be returned when the NBMPworkflow 221 is created.

It may be appreciated that FIG. 3 provides only an illustration of oneimplementation and does not imply any limitations with regard to howdifferent embodiments may be implemented. Many modifications to thedepicted environments may be made based on design and implementationrequirements.

FIG. 4 is a block diagram 400 of internal and external components ofcomputers depicted in FIG. 1 in accordance with an illustrativeembodiment. It should be appreciated that FIG. 4 provides only anillustration of one implementation and does not imply any limitationswith regard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environments may be madebased on design and implementation requirements.

Computer 102 (FIG. 1 ) and server computer 114 (FIG. 1 ) may includerespective sets of internal components 800A,B and external components900A,B illustrated in FIG. 4 . Each of the sets of internal components800 include one or more processors 820, one or more computer-readableRAMs 822 and one or more computer-readable ROMs 824 on one or more buses826, one or more operating systems 828, and one or morecomputer-readable tangible storage devices 830.

Processor 820 is implemented in hardware, firmware, or a combination ofhardware and software. Processor 820 is a central processing unit (CPU),a graphics processing unit (GPU), an accelerated processing unit (APU),a microprocessor, a microcontroller, a digital signal processor (DSP), afield-programmable gate array (FPGA), an application-specific integratedcircuit (ASIC), or another type of processing component. In someimplementations, processor 820 includes one or more processors capableof being programmed to perform a function. Bus 826 includes a componentthat permits communication among the internal components 800A,B.

The one or more operating systems 828, the software program 108 (FIG. 1) and the NBMP FLUS Control Program 116 (FIG. 1 ) on server computer 114(FIG. 1 ) are stored on one or more of the respective computer-readabletangible storage devices 830 for execution by one or more of therespective processors 820 via one or more of the respective RAMs 822(which typically include cache memory). In the embodiment illustrated inFIG. 4 , each of the computer-readable tangible storage devices 830 is amagnetic disk storage device of an internal hard drive. Alternatively,each of the computer-readable tangible storage devices 830 is asemiconductor storage device such as ROM 824, EPROM, flash memory, anoptical disk, a magneto-optic disk, a solid state disk, a compact disc(CD), a digital versatile disc (DVD), a floppy disk, a cartridge, amagnetic tape, and/or another type of non-transitory computer-readabletangible storage device that can store a computer program and digitalinformation.

Each set of internal components 800A,B also includes a R/W drive orinterface 832 to read from and write to one or more portablecomputer-readable tangible storage devices 936 such as a CD-ROM, DVD,memory stick, magnetic tape, magnetic disk, optical disk orsemiconductor storage device. A software program, such as the softwareprogram 108 (FIG. 1 ) and the NBMP FLUS Control Program 116 (FIG. 1 )can be stored on one or more of the respective portablecomputer-readable tangible storage devices 936, read via the respectiveR/W drive or interface 832 and loaded into the respective hard drive830.

Each set of internal components 800A,B also includes network adapters orinterfaces 836 such as a TCP/IP adapter cards; wireless Wi-Fi interfacecards; or 3G, 4G, or 5G wireless interface cards or other wired orwireless communication links. The software program 108 (FIG. 1 ) and theNBMP FLUS Control Program 116 (FIG. 1 ) on the server computer 114 (FIG.1 ) can be downloaded to the computer 102 (FIG. 1 ) and server computer114 from an external computer via a network (for example, the Internet,a local area network or other, wide area network) and respective networkadapters or interfaces 836. From the network adapters or interfaces 836,the software program 108 and the NBA/IP FLUS Control Program 116 on theserver computer 114 are loaded into the respective hard drive 830. Thenetwork may comprise copper wires, optical fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers.

Each of the sets of external components 900A,B can include a computerdisplay monitor 920, a keyboard 930, and a computer mouse 934. Externalcomponents 900A,B can also include touch screens, virtual keyboards,touch pads, pointing devices, and other human interface devices. Each ofthe sets of internal components 800A,B also includes device drivers 840to interface to computer display monitor 920, keyboard 930 and computermouse 934. The device drivers 840, R/W drive or interface 832 andnetwork adapter or interface 836 comprise hardware and software (storedin storage device 830 and/or ROM 824).

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,some embodiments are capable of being implemented in conjunction withany other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring to FIG. 5 , illustrative cloud computing environment 500 isdepicted. As shown, cloud computing environment 500 comprises one ormore cloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Cloud computingnodes 10 may communicate with one another. They may be grouped (notshown) physically or virtually, in one or more networks, such asPrivate, Community, Public, or Hybrid clouds as described hereinabove,or a combination thereof. This allows cloud computing environment 500 tooffer infrastructure, platforms and/or software as services for which acloud consumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 5 are intended to be illustrative only and that cloud computingnodes 10 and cloud computing environment 500 can communicate with anytype of computerized device over any type of network and/or networkaddressable connection (e.g., using a web browser).

Referring to FIG. 6 , a set of functional abstraction layers 600provided by cloud computing environment 500 (FIG. 5 ) is shown. Itshould be understood in advance that the components, layers, andfunctions shown in FIG. 6 are intended to be illustrative only andembodiments are not limited thereto. As depicted, the following layersand corresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and NBMP FLUS Control 96. NBMP FLUS Control96 may allow for a source client to be an NBMP source that may manage aworkflow through the FLUS control interface.

Some embodiments may relate to a system, a method, and/or a computerreadable medium at any possible technical detail level of integration.The computer readable medium may include a computer-readablenon-transitory storage medium (or media) having computer readableprogram instructions thereon for causing a processor to carry outoperations.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program code/instructions for carrying out operationsmay be assembler instructions, instruction-set-architecture (ISA)instructions, machine instructions, machine dependent instructions,microcode, firmware instructions, state-setting data, configuration datafor integrated circuitry, or either source code or object code writtenin any combination of one or more programming languages, including anobject oriented programming language such as Smalltalk, C++, or thelike, and procedural programming languages, such as the “C” programminglanguage or similar programming languages. The computer readable programinstructions may execute entirely on the user's computer, partly on theuser's computer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (LAN) or a wide area network (WAN), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider). In some embodiments,electronic circuitry including, for example, programmable logiccircuitry, field-programmable gate arrays (FPGA), or programmable logicarrays (PLA) may execute the computer readable program instructions byutilizing state information of the computer readable programinstructions to personalize the electronic circuitry, in order toperform aspects or operations.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer readable media according to variousembodiments. In this regard, each block in the flowchart or blockdiagrams may represent a module, segment, or portion of instructions,which comprises one or more executable instructions for implementing thespecified logical function(s). The method, computer system, and computerreadable medium may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in theFigures. In some alternative implementations, the functions noted in theblocks may occur out of the order noted in the Figures. For example, twoblocks shown in succession may, in fact, be executed concurrently orsubstantially concurrently, or the blocks may sometimes be executed inthe reverse order, depending upon the functionality involved. It willalso be noted that each block of the block diagrams and/or flowchartillustration, and combinations of blocks in the block diagrams and/orflowchart illustration, can be implemented by special purposehardware-based systems that perform the specified functions or acts orcarry out combinations of special purpose hardware and computerinstructions.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwaremay be designed to implement the systems and/or methods based on thedescription herein.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

The descriptions of the various aspects and embodiments have beenpresented for purposes of illustration, but are not intended to beexhaustive or limited to the embodiments disclosed. Even thoughcombinations of features are recited in the claims and/or disclosed inthe specification, these combinations are not intended to limit thedisclosure of possible implementations. In fact, many of these featuresmay be combined in ways not specifically recited in the claims and/ordisclosed in the specification. Although each dependent claim listedbelow may directly depend on only one claim, the disclosure of possibleimplementations includes each dependent claim in combination with everyother claim in the claim set. Many modifications and variations will beapparent to those of ordinary skill in the art without departing fromthe scope of the described embodiments. The terminology used herein waschosen to best explain the principles of the embodiments, the practicalapplication or technical improvement over technologies found in themarketplace, or to enable others of ordinary skill in the art tounderstand the embodiments disclosed herein.

What is claimed is:
 1. A method for establishing Network-Based Media Processing (NBMP) workflow through a 5G Framework for Live Uplink Streaming (FLUS) control, executable by a processor, comprising: discovering a sink and a network capability of a network platform; creating an NBMP workflow between an NBMP source and the sink, via a FLUS source and a FLUS sink; and tunneling information between the NBMP source and an NBMP workflow manager through a control interface for the FLUS source and the FLUS sink, to manage the NBMP workflow.
 2. The method of claim 1, wherein the network capability is described by an identifier and by a uniform resource locator (URL) location from which a description of the network capability is retrieved.
 3. The method of claim 2, wherein the description of the capability comprises an NBMP scheme identifier indicating that the NMBP workflow manager supports NBMP, the URL location, and a capability description document that describes the capability.
 4. The method of claim 1, wherein the network capability is explicitly included in a discovery response.
 5. The method of claim 1, wherein discovering the sink comprises the NBMP source making a request to the FLUS source.
 6. The method of claim 1, wherein a hypertext transfer protocol (HTTP) status code is returned based on the creation of the NBMP workflow.
 7. The method of claim 1, wherein the FLUS sink sends a request to the NBMP workflow manager to get the current platform capability.
 8. A computer system for establishing Network-Based Media Processing (NBMP) workflow through a 5G Framework for Live Uplink Streaming (FLUS) control, the computer system comprising: one or more computer-readable non-transitory storage media configured to store computer program code; and one or more computer processors configured to access said computer program code and operate as instructed by said computer program code, said computer program code including: discovering code configured to cause the one or more computer processors to discover a sink and a network capability of a network platform; creating code configured to cause the one or more computer processors to create an NBMP workflow between an NBMP source and the sink, via a FLUS source and a FLUS sink; and tunneling code configured to cause the one or more computer processors to tunnel information between the NBMP source and an NBMP workflow manager through a control interface for the FLUS source and the FLUS sunk, to manage the NBMP workflow.
 9. The computer system of claim 8, wherein the network capability is described by an identifier and by a uniform resource locator (URL) location from which a description of the network capability is retrieved.
 10. The computer system of claim 9, wherein the description of the capability comprises an NBMP scheme identifier indicating that the NMBP workflow manager supports NBMP, the URL location, and a capability description document that describes the capability.
 11. The computer system of claim 8, wherein the network capability is explicitly included in discovery responses.
 12. The computer system of claim 8, wherein discovering the sink comprises the NBMP source making a request to the FLUS source.
 13. The computer system of claim 8, wherein a hypertext transfer protocol (HTTP) status code is returned based on the creation of the NBMP workflow.
 14. The computer system of claim 8, wherein the FLUS sink sends a request to the NBMP workflow manager to get the current platform capability.
 15. A non-transitory computer readable medium having stored thereon a computer program for establishing Network-Based Media Processing (NBMP) workflow through a 5G Framework for Live Uplink Streaming (FLUS) control, the computer program configured to cause one or more computer processors to: discover a sink and a network capability of a network platform; create an NBMP workflow between an NBMP source and the sink, via a FLUS source and a FLUS sink; and tunnel information between the NBMP source and an NBMP workflow manager through a control interface for the FLUS source and the FLUS sink, to manage the NBMP workflow.
 16. The computer readable medium of claim 15, wherein the network capability is described by an identifier and by a uniform resource locator (URL) location from which a description of the network capability can be retrieved.
 17. The computer readable medium of claim 16, wherein the description of the capability comprises an NBMP scheme identifier indicating that the NMBP workflow manager supports NBMP, the URL location, and a capability description document that describes the capability.
 18. The computer readable medium of claim 15, wherein the network capability is explicitly included in discovery responses.
 19. The computer readable medium of claim 15, wherein discovering the sink comprises the NBMP source making a request to the FLUS source.
 20. The computer readable medium of claim 15, wherein a hypertext transfer protocol (HTTP) status code is returned based on the creation of the NBMP workflow. 